<?php
/**
 * <https://y.st./>
 * Copyright © 2016 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'Custom exception classes for include.d',
	'body' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/11/01.jpg" alt="Red berries" class="weblog-header-image" width="811" height="480" />
<p>
	Current countdowns:
</p>
<ul>
	<li>247 scheme-specific $a[URI]-parsing classes to write and add to <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d/releases">include.d</a></li>
	<li>1 free elective left in my associate degree program</li>
	<li>4 free electives left in my bachelor degree program</li>
</ul>
<p>
	Topics for essays that I want to write outside of school:
</p>
<ul>
<li>How the $a[GFDL] isn&apos;t a free license, and is effectively nonfree even when invariant sections aren&apos;t used</li>
<li>How the telephone number system is screwy</li>
<li>How postpaid mobile plans are bad for customers</li>
<li>How connections using &quot;untrusted&quot; $a[TLS] certificates are more trustworthy than connections without any $a[TLS] certificate at all</li>
<li>The importance of free software</li>
<li>The importance of free media</li>
</ul>
<p>
	I set up the exception framework that I talked about yesterday, and have now released a new version of <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d/releases">include.d</a>.
	This really is a minor update, but it paves the way for future work.
	The $a[URI] branch is going to see many exception-throwing instances added by the time that it finishes.
	It&apos;ll be much easier to fix up my use of exceptions now so I have fewer to go back and replace later.
</p>
<p>
	I&apos;ve also started making commits in the <code>master</code> branch of the Git repository, a practice that I was avoiding once I started using other branches.
	The idea had been that the stable version of include.d was available from that branch.
	However, I made my release a bit too early, so I didn&apos;t think of a couple things that I should have coded and later went back to touch them up.
	These things weren&apos;t big enough to warrant another release, but keeping a side branch to remember to tuck into the next release seems inefficient.
	I&apos;ve already started using Gogs&apos; &quot;release&quot; feature, so there&apos;s no need to additionally keep the <code>master</code> branch at a stable position.
	From here on out, I&apos;ll use the <code>master</code> branch for small touch ups that should exist in every branch, in addition to any stable code that, again, needs to find its way into the other branches.
</p>
<p>
	It looks like my old count of the number of $a[URI] schemes left to build $a[PHP] classes for was somehow off by two, so I&apos;ve corrected that in my notes.
	I still have 247 schemes left to go though.
	I had hoped to finish one scheme per day, but that was far too ambitious.I knew that I wouldn&apos;t be able to keep that up once school was back in session, but I was hoping to make decent progress until that point.
	At this rate, it&apos;s going to take <strong>*years*</strong> to finish the $a[URI] update for include.d.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
